Click any tag below to further narrow down your results
+ careers
(2)
+ sql
(1)
+ semantic layers
(1)
+ data analytics developers
(1)
+ data analyst role
(1)
+ dashboard generation
(1)
+ validation
(1)
+ software burnout
(1)
+ ux designers
(1)
+ layoffs
(1)
+ delegation
(1)
+ software engineering
(1)
+ technological progress
(1)
+ luddites
(1)
+ hypocrisy
(1)
Links
Sean Goedecke argues that software engineers have no moral standing to resist AI automation, since the entire profession has always been about automating other people's jobs. He compares engineers opposing AI to the mechanics who built power looms and then complained when their own skills became obsolete.
- Software engineering's core purpose is automating human labor—from spreadsheets displacing bookkeepers to software eliminating video rental stores, travel agencies, and data entry jobs. Engineers can't claim this is suddenly wrong now that it's happening to them.
- The historical parallel to Luddites doesn't work: software engineers are like the mechanics who built the automation machines, not the workers being displaced. Those same mechanics were automated away 50 years later and were seen as hypocrites for resisting it.
- If engineers genuinely believe technological progress is harmful, they should quit. Complaining about AI while continuing to build automation is intellectually dishonest—it's "pulling the ladder up behind you" only after you've climbed it.
The speaker argues that burnout and early quitting among software developers and UX designers are rising, and that this is driven by layoffs, AI-driven automation that cuts people off from their work, and incentives that favour replacing experienced staff with cheaper, overworked workers. He ends by urging people in the field to accept the change and start planning an exit.
- Developers and UX designers who embraced AI are now quitting, often citing that the work stopped being enjoyable and emotionally draining, not that they opposed the technology.
- Layoffs leave fewer people doing the same workload, and AI tools feel more like delegation than craft, which removes the satisfaction of ownership and the flow state that makes coding engaging.
- Quitting doesn't earn severance and can be replaced by a cheaper hire from a pool of unemployed developers, so the incentives of employers reward keeping this pressure in place.
A data analyst describes how AI tools enabled a nontechnical product manager to build complex, client‐ready dashboards spanning hundreds of data sources. After validating the results and finding few errors, the author realizes that core analytics tasks once thought AI‐proof are now automated.
- A nontechnical PM used an AI tool to build a client-ready dashboard across hundreds of data sources with minimal hallucinations, in minutes instead of weeks.
- The data analyst's role shifted from hands-on querying/dashboard-building to validation, governance, schema design, and writing guardrails.
- Core analytics tasks once assumed automation-proof (writing queries, wrangling data, building visualizations) are now being handled by AI.
- Remaining human value lies in strategy: choosing metrics, designing experiments, prompt design, bias detection, and communicating results.
Since the inception of SQL in 1974, there has been a recurring dream to replace data analytics developers with tools that simplify the querying process. Each decade has seen innovations that aim to democratize data access, yet the complex intellectual work of understanding business needs and making informed decisions remains essential. Advances like AI can enhance efficiency but do not eliminate the crucial human expertise required in data analytics.
- SQL was designed in 1974 by IBM's Chamberlin and Boyce specifically to let non-programmers query data in plain English, yet this self-service dream has resurfaced every decade (OLAP in the 80s, semantic layers now) without ever eliminating the need for developers.
- AI can now generate SQL and build analytical models faster than ever, but it automates only the mechanical coding, not the judgment calls about which metrics or definitions actually matter.
- The real bottleneck was never syntax or tooling but the intellectual work of understanding business context — a gap AI accelerates around but doesn't close.